I think "release" is a more natural name for this workflow as it cuts a release.
(I don't usually here people refer to that as "pushing a gem").

In addition, I've updated all dependent actions to the latest versions to try
to fix a failure I just got on my last attempt at running it:

```
Run ruby/setup-ruby@cacc9f1
  with:
    working-directory: config/release
    bundler-cache: true
    ruby-version: ruby
Error: The current runner (ubuntu-24.04-x64) was detected as self-hosted because the platform does not match a GitHub-hosted runner image (or that image is deprecated and no longer supported).
In such a case, you should install Ruby in the $RUNNER_TOOL_CACHE yourself, for example using https://github.com/rbenv/ruby-build
You can take inspiration from this workflow for more details: https://github.com/ruby/ruby-builder/blob/master/.github/workflows/build.yml
$ ruby-build 3.3.1 /opt/hostedtoolcache/Ruby/3.3.1/x64
Once that completes successfully, mark it as complete with:
$ touch /opt/hostedtoolcache/Ruby/3.3.1/x64.complete
It is your responsibility to ensure installing Ruby like that is not done in parallel.
```

As per ruby/setup-ruby#595, it appears that updating
the version of this action will fix the error. While I'm at it I went ahead
and updated the others, too.